Do we need this, while working in docker?

By environment I meant production / RC / local. I am not sure if deployed envs' configuration will differ.

Isn't it too specific? As I understand rollback means reversed migration (does it?), in which case we would hardly ever use that field and even if we do, "Migrations" still seems to be the likely place I would mention it

Defaultly it would be N/A (or the previous version mentioned), but I would stick with that as a good practice. Nevertheless could be removed. ;-)

I don't think that there's much of use out of it, we can probably assume that every member is using a "recent enough" one.

Ditto, I would leave it as a good practice.

What does it mean? Should I list unit tests here? Or describe what I (potentially) added to the testing suite?

When you don't have a habit of writing tests this could be actually self-reflective. "Oh so... I wrote this function so what kind of tests do I need here? Since it is expected to list sth...".

Also this could be early checker for complexity od the code. If you have a lot of those the chance is that you like spaghetti, aren't you? :D

Hard-copy from other project. :D Could be removed.

👍 💯